home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
mc_cbv10.zip
/
MC_CBV.DOC
< prev
next >
Wrap
Text File
|
1993-03-16
|
16KB
|
367 lines
===============================================================================
Program : MC_CBV Version : 1.00
Contact : Rod Hancock Date : Mar 16, 1993
Voice : (416) 404-2756 FidoNet : 1:229/418
===============================================================================
MC_CBV
Automated Callback verifier
for
RemoteAccess
Copyright 1992,1993 Motor City Software
All Rights Reserved
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Introduction ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
This is Motor City Software's CallBack Verification System for RemoteAccess.
This version is written to work with RemoteAccess V1.1x and V2.00 GAMMA.
If the User has less than 10 Minutes remaining when they enter the CallBack
Door, they will have their time reset to 10 minutes in order to allow them
to complete the CallBack Process.
The Following Sysop Keys are available:
Alt-C Chat With User
Alt-J Jump To Dos
Alt-R Return To BBS
UpArrow Add 1 Minutes Time
DownArrow Deduct 1 Minutes Time
While MC_CBV is calling the user back, you may abort by hitting ESCAPE.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Setup ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
Run CBVSetup to configure the CallBack Verifier.
SYSTEM INFORMATION
==================
Full Path to Users.BBS
This is the full path, including trailing backslash to your USERS.BBS This
is used to find the Users.BBS (If scanning it for dupe #'s) and the Message
base files.
Your City & State Location
The location of your BBS. This should be accurate, as it is used when
asking the user if the phone number is correct when dialed from this
location. Eg. Does 555-5555 look correct to call you from Oshawa Ontario?
Use RA Extended Log Format
Not implemented yet (uses Extended RA log format)
Choose Phone Number Format
"0" for US style
"1" for European style (This door hasn't been tested using Unformatted #'s)
Check for Duplicate Number
"0" Do Not Check For Dupes
"1" Check Numbers Already Called by MC-CBV
"2" Check Voice & Data Numbers From USERS.BBS
If Set to "1" or "2" then this will force the CBV to REFUSE to call a
duplicate number. Note this will be a problem if you have more than one
user in a family for instance. NOTE, The Callback Door KNOWS which version
of RemoteAccess you are using, and will use the correct USERS.BBS
structures when reading that file.
Message Base To Use
If you want the Callback Door to send messages to the Sysop or User, then
you may enter the message base # here. If you set it to 0, then CBV will
NOT post any messages. NOTE this supports ONLY the Hudson Message Base.
MODEM INFORMATION
=================
Modem Init STRING
String to initialize your modem. MUST include | on end of string!
Make Long Distance CallBack
Allow LD users to do callback?
# of Times to Redial Number
How many time should you try to call the user back.
# of PassWord Attempts to allow
Give the user how many tries at their password?
Wait How Long for Carrier
Time to allow for your modem to hangup on the user, call the user back,
wait for the user to figure out how to type in ATA and hit Enter, and for
the modem to connect to the person it called. You must also allow time for
the user to figure out your modem is calling and type in ATA and hit Enter
until their modem responds. Remember, a lot of users have internal modems
with no lights so keep this in mind. AT LEAST 30 seconds is recommended.
Delay Before Redail Number
Wait how long between retries to callback the user.
Dial Out Prefix
ATDT or ATDP normally
Long Distance Prefix
Number added before hpone number to call Long Distance numbers, normally
1- in the US.
Your Area Code
Your LOCAL area code.
Hangup After L/D Call
If you allow LD call backs, should MC_CBV hangup immediately after the
callback is successful? (ie. If you say no here YOU WILL have to pay for
the user to use your BBS for however long they take on this call.
Hangup After Local Call
Same as hangup after LD for those cases where YOU have to pay for the
phone call.
USER INFORMATION
================
Validate Via Auto EMSI
If the user logged on using EMSI should they be automatically validated?
Log Off Twit Not-Valid User
Should the program hang up on a user that the system is configured to be
able to callback, but refuses to use it?
LockOut Twit Not-Valid User
Should the program LOCK OUT a user that the system is configured to be
able to callback, but refuses to use it?
Allow User to Change Number
Should the user be allowed to enter another phone number to call their
modem at? An example would be the user is calling from a friends house
etc.
Make Bulletin of Twit Users
Should a list of those who, for one reason or another, refuse to use the
callback?
Min Level to NOT Use CBV
Security level at which the program should just exit and tell the user that
he/she is already validated.
Validated New CBV Flags
RA user flags to give a user who successfully completes the callback.
This also includes Long Distance and IEMSI users if you validate them
without calling them.
The following characters may be entered here:
X Turn This Flag ON
- Turn This Flag OFF
? DO NOT Change This Flag
* Toggle This Flag (If ON, Turn It OFF, If OFF, Turn It ON)
UpDate Users Security After
Should MC_CBV raise the users security level if they do the callback right?
Validated Security Level
Security level to give a user who uses the callback successfully.
Security Level for LD User
Security to give an LD caller if you don't allow LD callbacks.
Non-Validated User SubDays
Registered Version Only
If this is 0, then the users Subscription Expiry Date is NOT updated.
You may enter a number from 1 to 1000 for the number of days until the
users BBS Account expires. This is for users who would not use the CBV
or those who did not reconnect and get updated.
Validated User SubDays
Registered Version Only
If this is 0, then the users Subscription Expiry Date is NOT updated.
You may enter a number from 1 to 1000 for the number of days until the
users BBS Account expires. This is for users who the CBV DID call back
and reconnect with. This includes IEMSI logons if you update them without
callback.
Long Distance User SubDays
Registered Version Only
If this is 0, then the users Subscription Expiry Date is NOT updated.
You may enter a number from 1 to 1000 for the number of days until the
users BBS Account expires. This is for Long Distance users if you do not
allow LD Callbacks.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Command line parameters ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
Usage: MC_CBV /N2 /NoAC
/N Defines the node number using CBV. You may use /N*N on the optional data
line in the RA Menu option.
/NoAC If the number is in your area code, but not a local call, then do NOT
dial the area code. It will still insert a 1- before the number but
the area code is stripped out.
Example: D:\BBS\CBV\MC_CBV.EXE /N*N
If No Command Line Parameters are used, then it defaults to NODE 1.
Place MM_CBV.EXE in its own directory, and call the MC_CBV.EXE from your
Top Menu as a type 7. It will look for the EXITINFO.BBS and DORINFO1.DEF
in the CURRENT Directory.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Optional Message Template Files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
MC_CBV will Post Messages to the Sysop if certain Message Template Files
exist AND you have chosen a valid Hudson Message Base in CBVSetup. These
files are ASCII Text files created using any text editor. We have included
samples in an archive called MESSAGES.ARJ In each of these files, you will
notice that line 1 contains the SUBJECT of the message. The rest of the lines
may contain whatever you like, and the following TextFile Control Codes are
Valid. (As used in RemoteAccess)
^FA - Current Users Full Name
^FO - Current Users Security Level
^F4 - Date of Current Users FIRST Call to BBS
^F6 - Current Users Subscription Expiry Date
^FE - Current Users Voice Phone Number
^FD - Current Users Data Phone Number
^F3 - Current Users Handle
^FB - Current Users Location
The following Templates have been included, and if they exist, and a valid
Hudson Message Base has been chosen, will cause a message to be written. Feel
free to modify these as you see fit.
NONEED.MSG - Registered Version Only
If this template exists in the same directory as MC_CBV.EXE
and a user has a high enough security level to exempt them
from using CBV, this message will be posted to alert you.
NOTUSED.MSG - Registered Version Only
If this template exists in the same directory as MC_CBV.EXE
and the user for whatever reason does NOT use the CBV, then
this will alert you. Once the template has been posted, a
one line Reason is added to the message, explaining where
the user Quit.
VERIFIED.MSG - Registered Version Only
If this template exists in the same directory as MC_CBV.EXE
then this message will be posted to you when the user has
completed the callback process.
LDUPDATE.MSG - Registered Version Only
If this template exists in the same directory as MC_CBV.EXE
and you update LD callers without calling them back, this
message will be posted to you.
IEMSI.MSG - Registered Version Only
If this template exists in the same directory as MC_CBV.EXE
and you automatically update IEMSI users, then this message
will be posted to you.
FAILPW.MSG - Registered Version Only
If this template exists in the same directory as MC_CBV.EXE
and the user reconnects, but gets the password wrong, then
this message will be posted to you.
WELCOME.MSG - If this template exists in the same directory as MC_CBV.EXE
then it will be posted to the USER when they are verified.
This will include IEMSI and LD users if you update them
without doing the callback. This can be used to give them
more information about joining your BBS, or anything you
desire. This message will be posted TO the User, From the
Sysop as defined in Dorinfo1.Def
NOTE: If you are NOT registered, then the ONLY Message that you may post is
WELCOME.MSG to the user. A reminder is written to the end of this
message stating that this is an Unregistered Evaluation Copy, and
requires registration after evaluating it.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Optional Information text files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
MC_CBV allows up to 7 text files to be used to describe the door for the
users. If the file isn't present then MC_CBV will use default text. These
files should be located in the same directory as MC_CBV.EXE Samples of these
files are included in the archive CBV_TEXT.ARJ
Brief descriptions are as follows:
The files support the RA Text File Control Codes for UserName, Phone Numbers
etc.
ADDPHONE.TXT - Displayed to user before showing ASKPHONE.TXT
ASKPHONE.TXT - Message to the User to see if the phone number looks right
before before calling.
EXPLAIN.TXT - If the user did not understand how to use the CBV, then this
is where you may try to explain it one last time. If they
still do not understand, then the door will exit and you will
have to verify them another way, or they may try again.
LOCHANG.TXT - Tells the User why the door is hanging up on them after a
successful local callback.
LDHANG.TXT - Tells the User why the door is hanging up on them after a
successful long distance callback.
NO_LD.TXT - Shown to Long Distance users if you don't allow LD calls.
PRECALL.TXT - Shown just prior to dialing the users number and explains how
to make their modem answer when they are called.
TELSYSOP.TXT - Message to user if they say the number the door will call
them at doesn't look right.
UINFO.ANS - This is the User Information Screen. This one allows you to
create an ANS and an ASC version.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Data text files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
Samples are provided in the archive EXAMPLES.ARJ
Data Text files: (* - means it's required)
* MC_CBV.LOC - List of the AREA CODE AND First 3 Numbers of phone numbers
that are local to you. Example 416-579 If the area code is
the same as that in CBVSetup, then it is stripped from the
phone number when it is dialed. If you have OTHER area codes
which are local, then you may also add them to this file, and
the area code will NOT be stripped when those are dialed. The
number will simply be dialed as AAA-NNN-NNNN where AAA is the
area code, and NNN-NNNN is the rest of the number. IF you MUST
dial a 1 in front of this 'local' area code, you may add a 1-
in FRONT of the AREA CODE in the MC_CBV.LOC file. For example,
804-256 is local, but requires a 1 in front, then you put
1-804-256 in here and it will dial the 1 first. I am not very
familiar with having more than one local area code, so if you
have ANY problems, contact us and we'll fix it up for your
particular needs.
YOU MUST MAKE THIS FILE!
MC_CBV.LOG - Log of the doors activity. Made by the door.
MC_CBV.BAD - List of phone number NOT TO CALL (ie your local police station
fire station, etc.) MC_CBV will automatically not call 411,
911, 900 numbers and 555-1212 (directory assistance). You have
to make this file if you want to define other Bad Numbers.
MC_CBV.OK - List of numbers the door has successfully called.
MC_CBV.TWT - Semi-informative Log of twits using the door.